Make GeoZarr quicklook discovery tolerant of missing datasets #35
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
/quality/l2a_quicklook, and a backfill sweep showed June 2025cpm_v256items (e.g.S2A_MSIL2A_20250606T141751_N0511_R110_T22WFS_20250606T183809) were already missing the dataset, so discovery based on STAC alone left the CLI crashing while we wait on the next upstream update from the EODC store.Evidence
cpm_v256) curl of/quality/l2a_quicklook/.../.zattrs-> HTTP 404 while STAC still lists the asset.cpm_v262) curl -> HTTP 404, jq on.zattrsshowsnull, STACassets.l2a_quicklookisnull.cpm_v256) reveals missing quicklook datasets as early asS2A_MSIL2A_20250606T141751_N0511_R110_T22WFS_20250606T183809.What Changed
scripts/convert.py: filter and mark quicklook groups as optional; continue when downloads 404.README.md: adds a “Quicklook Availability” section summarizing sampling results and guidance for operators.Linked PR in data-model EOPF-Explorer/data-model#57